Release 10.1A: OpenEdge Development:
Messaging and ESB

Implementing Messaging

In order to exchange messages using JMS messaging model, a 4GL client establishes a connection to a SonicMQ Broker, creates the message, and sends the message to a receiver. The following sections describe:

Managing connections and sessions
Externally managed connections
Working with messages
Consuming messages
Transaction and recovery procedures
Error and condition handling

Programming instructions are provided in Chapter 5, " Programming for the OpenEdge Adapter for SonicMQ with the 4GL-JMS API."

For an alphabetical API reference, see Appendix A "4GL-JMS API Reference."